Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gh-85747: "Preface" section of asyncio-eventloop.rst: Switch to active voice and suggest other edits #99784

Merged
merged 3 commits into from
Dec 4, 2022

Conversation

bskinn
Copy link
Contributor

@bskinn bskinn commented Nov 25, 2022

As per discussion in #85747, a very small PR focused just on the "Preface" section of asyncio-eventloop.rst.

In addition to a couple of switches from passive to active voice, I've also suggested a few other edits that, to me, improve clarity. Please advise if proposed edits of this sort are welcome as a part of this effort of #85747, or if PRs should stick ~strictly to passive->active voice edits.

"Preface" section of asyncio-eventloop.rst.

As per python#85747.
Comment on lines 61 to 64
Emits a deprecation warning if there is no running event loop.
In future Python releases, this function will become an alias of
:func:`get_running_loop` and will accordingly raise a
:exc:`RuntimeError` if there is no running event loop.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately, while for a long time that was indeed the plan, we are considering undeprecating it, based on feedback received from users who rely on this (see #93453). Maybe all we need to do, while this is as yet undecided, is to say "may" instead of "will"?

Copy link
Contributor Author

@bskinn bskinn Nov 30, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, reading the discussion, I think a switch to "may" would suffice.

Would it be good/useful also to link to that ongoing discussion, from this point in the docs? Or is the philosophy of the docs to avoid that kind of contemporaneity?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would skip the link, it will just confuse folks. We'll update these docs once we are sure.

Hopefully this PR can be backported to 3.11 and maybe 3.10.

@bedevere-bot
Copy link

A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated.

Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request.

And if you don't make the requested changes, you will be put in the comfy chair!

@bskinn
Copy link
Contributor Author

bskinn commented Dec 2, 2022

I have made the requested changes; please review again

@bedevere-bot
Copy link

Thanks for making the requested changes!

@gvanrossum: please review the changes made to this pull request.

@gvanrossum gvanrossum merged commit bf26bdf into python:main Dec 4, 2022
@miss-islington
Copy link
Contributor

Thanks @bskinn for the PR, and @gvanrossum for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10, 3.11.
🐍🍒⛏🤖

@bedevere-bot
Copy link

GH-99980 is a backport of this pull request to the 3.11 branch.

@bedevere-bot bedevere-bot removed the needs backport to 3.11 only security fixes label Dec 4, 2022
miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Dec 4, 2022
… active voice and suggest other edits (pythonGH-99784)

(cherry picked from commit bf26bdf)

Co-authored-by: Brian Skinn <brian.skinn@gmail.com>
@bedevere-bot
Copy link

GH-99981 is a backport of this pull request to the 3.10 branch.

@bedevere-bot bedevere-bot removed the needs backport to 3.10 only security fixes label Dec 4, 2022
miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Dec 4, 2022
… active voice and suggest other edits (pythonGH-99784)

(cherry picked from commit bf26bdf)

Co-authored-by: Brian Skinn <brian.skinn@gmail.com>
miss-islington added a commit that referenced this pull request Dec 4, 2022
…e voice and suggest other edits (GH-99784)

(cherry picked from commit bf26bdf)

Co-authored-by: Brian Skinn <brian.skinn@gmail.com>
miss-islington added a commit that referenced this pull request Dec 4, 2022
…e voice and suggest other edits (GH-99784)

(cherry picked from commit bf26bdf)

Co-authored-by: Brian Skinn <brian.skinn@gmail.com>
@bskinn bskinn deleted the active-voice-asyncio-1 branch December 4, 2022 01:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Documentation in the Doc dir skip news
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants